Repository navigation
Expose x86 KVM state and execution control for PC guests - #210
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Expose x86 KVM execution and architectural state so trex can supply PC firmware and devices and boot NT 3.1 in process. This is the hypervisor dependency of tinyrange/trex#37.
Validation completed during implementation: the focused x86 KVM real-mode interrupt/execution test and trex backend/device tests passed. Fresh NT 3.1 VGA and RAM-display images booted; Notepad, the Security dialog and Win16 Write worked. The browser integration was also verified with Firefox. The initial supported host is Linux/amd64 with KVM.
Recipes and integration smokes: https://github.com/tinyrange/tinyrangex/pull/67. Merge this dependency before trex #37, then the recipe PR.